![]() |
![]() |
![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
![]() |
To access the contents, click the chapter and section titles.
Oracle Performance Tuning and Optimization
SummaryPart I of this book reviewed the Oracle architecture, studied the attributes of a well-tuned system, and looked at the methodology for performance engineering. It also looked at some of the ways you can test performance with benchmarks and how you can monitor the results both through Oracle and third-party products. Finally, you have seen how you can engineer performance into the system at all stages of implementation, from design and test to production. Chapter 2, Understanding Terms, started out by reviewing how Oracle operates, that is, how all its components work together. This review should give you a basis for many of the tuning concepts covered in Part II, Tuning the Server. Chapters 3 and 4 introduced the concept of a well-tuned system and a methodology you can follow to achieve such a system. By understanding the attributes of a good performing system, it may be easier to set goals for your system. Remember that these attributes include good response times as well as high throughput rates. The following parts of the book discuss ways to tune for a specific property such as fast response time or good throughput. Chapter 5, Benchmarking, should have impressed you with the amount of effort involved in creating and running a benchmark. You can use the information in that chapter to help in your next system-purchasing decision. The chapter also looked at some of the attributes of a custom benchmark or workload generator. If you have the opportunity to build a test system, you will see much benefit in both your performance and debugging efforts. Chapter 6, Performance Monitoring Tools, introduced you to some of the products and features of Oracle you may not already be familiar with. Numerous examples in the upcoming chapters use these tools extensively. Finally, this chapter explained that tuning doesnt have to be left to the test and production phases (when the application is already completed and ready for rollout). Try to influence the design phase. Look for ways to improve performance when the application is still on the drawing board. I hope that this introduction has given you enough background and review to prepare you for the rest of the book. The following parts of the book look in-depth at some of the performance problems frequently encountered and how to solve them.
|
![]() |
Products | Contact Us | About Us | Privacy | Ad Info | Home
Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc. All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited. |